home *** CD-ROM | disk | FTP | other *** search
- Path: access4.digex.net!not-for-mail
- From: ell@access4.digex.net (Ell)
- Newsgroups: comp.lang.c++
- Subject: MI in C++
- Date: 13 Jan 1996 04:03:03 GMT
- Organization: The Universe
- Message-ID: <4d7atn$abs@news4.digex.net>
- NNTP-Posting-Host: access4.digex.net
- X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
-
- From news3.digex.net!access2.digex.net!not-for-mail Fri Jan 12 23:00:11 1996
- Path: news3.digex.net!access2.digex.net!not-for-mail
- From: ell@access2.digex.net (Ell)
- Newsgroups: comp.object
- Subject: Re: Working without Multiple Inheritance
- Date: 7 Nov 1995 01:42:29 GMT
- Organization: Express Access Online Communications, Greenbelt, MD USA
- Lines: 19
- Message-ID: <47mdi5$b2h@news4.digex.net>
- References: <cpopetz-2610952243520001@jsr.isdn.uiuc.edu> <474q0t$5ql@newsbf02.news.aol.com>
- NNTP-Posting-Host: access2-2.digex.net
- X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
-
- D. Erway (derway@ndc.com) wrote:
- :..
- : Yeah, I knew that. I was responding to the guy who said you can only get
- : multiple class polymorphic behaviour on a single object by using full MI.
- : That is wrong.
-
- Right, I think MI comes into in to play with C++ when you want somewhat
- orthogonal behavior in the same abstraction. The point is to inherit from
- the abstract aggregate formed from its abstract mixin components. This
- can be the basis of swapping subsystems. Inherit concrete subsystem
- aggregates, consisting of related, yet orthogonal classes, from an MI
- created abstract aggregate, declare a pointer to the abstract aggregate,
- and then you'll be able to swap the concrete inherited aggregates in and
- out during run-time as needed.
-
- See my article "The Beauty and Power of C++" in the May '95 issue of Object
- magazine for a bit more on this.
-
- Elliott
-
-